sector1.bet was registered with GoDaddy.com, LLC on 18 Oct 2024 and is hosted on AS16509 Amazon.com Inc. in United States of America. Its SSL certificate from Amazon expired on 16 Nov 2025, and the site does not support HTTP/3.
What security vendors and the WOT community say about this domain.
Is sector1.bet’s name taken on other extensions?
Every IP address sector1.bet resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| sector1.bet | 3.168.122.118 | 60 |
| sector1.bet | 3.168.122.40 | 60 |
| sector1.bet | 3.168.122.50 | 60 |
| sector1.bet | 3.168.122.54 | 60 |
| Host | Name server | TTL |
|---|---|---|
| sector1.bet | ns-1195.awsdns-21.org | 21600 |
| sector1.bet | ns-1886.awsdns-43.co.uk | 21600 |
| sector1.bet | ns-203.awsdns-25.com | 21600 |
| sector1.bet | ns-533.awsdns-02.net | 21600 |
| Host | Start of authority | TTL |
|---|---|---|
| sector1.bet | ns-533.awsdns-02.net awsdns-hostmaster.amazon.com 1 7200 900 1209600 86400 | 900 |
Other domains served from 3.168.122.54. Normal for shared hosting and CDNs.
No reviews yet. Used sector1.bet? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
sector1.bet has no community safety rating yet. Its SSL certificate expired on 16 Nov 2025. See Security →
sector1.bet is registered through GoDaddy.com, LLC. The owner's details are hidden by a privacy service in the public WHOIS record. See WHOIS →
The registration expired on 18 Oct 2025. See Overview →
sector1.bet was registered on 18 Oct 2024, making it 1 year old. See Overview →
sector1.bet is served from 4 IP addresses, mainly on AS16509 Amazon.com Inc. in United States of America. See Hosting →
Raw registry data for sector1.bet. May be redacted by privacy services.
Domain Name: sector1.bet Registry Domain ID: d8e00c9bcdd741bea1372205fcbdf536-DONUTS Registrar WHOIS Server: whois.godaddy.com/ Registrar URL: http://www.godaddy.com/domains/search.aspx?ci=8990 Updated Date: 2024-10-23T16:57:48Z Creation Date: 2024-10-18T16:57:25Z Registry Expiry Date: 2025-10-18T16:57:25Z Registrar: GoDaddy.com, LLC Registrar IANA ID: 146 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +1.4805058800 Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited Name Server: ns-533.awsdns-02.net Name Server: ns-203.awsdns-25.com Name Server: ns-1886.awsdns-43.co.uk Name Server: ns-1195.awsdns-21.org DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://icann.org/wicf/ >>> Last update of WHOIS database: 2025-05-12T07:34:27Z <<< For more information on Whois status codes, please visit https://icann.org/epp Terms of Use: Access to WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the registry database. The data in this record is provided by Identity Digital or the Registry Operator for informational purposes only, and accuracy is not guaranteed. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Identity Digital except as reasonably necessary to register domain names or modify existing registrations. When using the Whois service, please consider the following: The Whois service is not a replacement for standard EPP commands to the SRS service. Whois is not considered authoritative for registered domain objects. The Whois service may be scheduled for downtime during production or OT&E maintenance periods. Queries to the Whois services are throttled. If too many queries are received from a single IP address within a specified time, the service will begin to reject further queries for a period of time to prevent disruption of Whois service access. Abuse of the Whois system through data mining is mitigated by detecting and limiting bulk query access from single sources. Where applicable, the presence of a [Non-Public Data] tag indicates that such data is not made publicly available due to applicable data privacy laws or requirements. Should you wish to contact the registrant, please refer to the Whois records available through the registrar URL listed above. Access to non-public data may be provided, upon request, where it can be reasonably confirmed that the requester holds a specific legitimate interest and a proper legal basis for accessing the withheld data. Access to this data provided by Identity Digital can be requested by submitting a request via the form found at https://www.identity.digital/about/policies/whois-layered-access/. The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Identity Digital Inc. and Registry Operator reserve the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.
The first response from http://www.sector1.bet, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with sector1.bet. Data is collected independently from public sources and some figures are estimates, provided for information only.
Spam and malware blocklists for the site's IP and mail servers.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.