Alternatives to naughtytrigger.com
Matched automatically on description, category and technology. Only sites that pass our safety checks are shown. · Report a wrong match
naughtytrigger.com was registered with whois.verisign-grs.com on 3 Oct 2019 and is hosted on AS14618 Amazon.com Inc. in United States of America. Its SSL certificate from Amazon expired on 23 Nov 2024, and the site does not support HTTP/3. WOT's community rates its safety excellent (80/100).
What security vendors and the WOT community say about this domain.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
1 similar domain registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| naughtytrigger.xyz | Other extension | 22 Oct 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is naughtytrigger.com’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| United States | 79.2% | — | — | — |
| Canada | 7.9% | — | — | — |
| United Kingdom | 7.1% | — | — | — |
| Lithuania | 1.8% | — | — | — |
| Estonia | 1.3% | — | — | — |
2 technologies detected across 1 category.
Detected from headers, page source and DNS · Automatic and may be incomplete · Suggest a correction
Every IP address naughtytrigger.com resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| naughtytrigger.com | 3.218.12.171 | 60 |
| naughtytrigger.com | 35.171.210.76 | 60 |
| naughtytrigger.com | 54.87.235.71 | 60 |
| Host | Mail server | TTL |
|---|---|---|
| naughtytrigger.com | 1 aspmx.l.google.com | 300 |
| naughtytrigger.com | 5 alt1.aspmx.l.google.com | 300 |
| naughtytrigger.com | 5 alt2.aspmx.l.google.com | 300 |
| naughtytrigger.com | 10 alt3.aspmx.l.google.com | 300 |
| naughtytrigger.com | 10 alt4.aspmx.l.google.com | 300 |
| Host | Name server | TTL |
|---|---|---|
| naughtytrigger.com | ns-1187.awsdns-20.org | 21600 |
| naughtytrigger.com | ns-1908.awsdns-46.co.uk | 21600 |
| naughtytrigger.com | ns-248.awsdns-31.com | 21600 |
| naughtytrigger.com | ns-518.awsdns-00.net | 21600 |
| Host | Text | TTL |
|---|---|---|
| naughtytrigger.com | "v=spf1 include:_spf.google.com include:_spf.smtp.com include:amazonses.com include:_spf.sparkpostmail.com ip4:85.236.136.0/21 -all" | 300 |
| Host | Start of authority | TTL |
|---|---|---|
| naughtytrigger.com | ns-518.awsdns-00.net awsdns-hostmaster.amazon.com 1 7200 900 1209600 86400 | 900 |
No reviews yet. Used naughtytrigger.com? 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.
WOT's community rates naughtytrigger.com excellent for safety (80/100). Its SSL certificate expired on 23 Nov 2024. See Security →
naughtytrigger.com is registered through whois.verisign-grs.com. See WHOIS →
The registration expired on 3 Oct 2024. See Overview →
naughtytrigger.com was registered on 3 Oct 2019, making it 7 years old. See Overview →
naughtytrigger.com is served from 3 IP addresses, mainly on AS14618 Amazon.com Inc. in United States of America. See Hosting →
We detected 2 technologies, including jQuery and jQuery UI. See Built with →
Raw registry data for naughtytrigger.com. May be redacted by privacy services.
{"objectClassName":"domain","handle":"2439811869_DOMAIN_COM-VRSN","ldhName":"NAUGHTYTRIGGER.COM","links":[{"value":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/NAUGHTYTRIGGER.COM","rel":"self","href":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/NAUGHTYTRIGGER.COM","type":"application\/rdap+json"},{"value":"https:\/\/rdap.safenames.legal\/rdap\/domain\/NAUGHTYTRIGGER.COM","rel":"related","href":"https:\/\/rdap.safenames.legal\/rdap\/domain\/NAUGHTYTRIGGER.COM","type":"application\/rdap+json"}],"status":["client delete prohibited","client transfer prohibited","client update prohibited"],"entities":[{"objectClassName":"entity","handle":"447","roles":["registrar"],"publicIds":[{"type":"IANA Registrar ID","identifier":"447"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","SafeNames Ltd."]]],"entities":[{"objectClassName":"entity","roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:+44.1908200022"],["email",{},"text","[email protected]"]]]}]}],"events":[{"eventAction":"registration","eventDate":"2019-10-03T16:02:53Z"},{"eventAction":"expiration","eventDate":"2024-10-03T16:02:53Z"},{"eventAction":"last changed","eventDate":"2022-11-01T03:59:13Z"},{"eventAction":"last update of RDAP database","eventDate":"2023-10-26T23:01:57Z"}],"secureDNS":{"delegationSigned":false},"nameservers":[{"objectClassName":"nameserver","ldhName":"NS-1187.AWSDNS-20.ORG"},{"objectClassName":"nameserver","ldhName":"NS-1908.AWSDNS-46.CO.UK"},{"objectClassName":"nameserver","ldhName":"NS-248.AWSDNS-31.COM"},{"objectClassName":"nameserver","ldhName":"NS-518.AWSDNS-00.NET"}],"rdapConformance":["rdap_level_0","icann_rdap_technical_implementation_guide_0","icann_rdap_response_profile_0"],"notices":[{"title":"Terms of Use","description":["Service subject to Terms of Use."],"links":[{"href":"https:\/\/www.verisign.com\/domain-names\/registration-data-access-protocol\/terms-service\/index.xhtml","type":"text\/html"}]},{"title":"Status Codes","description":["For more information on domain status codes, please visit https:\/\/icann.org\/epp"],"links":[{"href":"https:\/\/icann.org\/epp","type":"text\/html"}]},{"title":"RDDS Inaccuracy Complaint Form","description":["URL of the ICANN RDDS Inaccuracy Complaint Form: https:\/\/icann.org\/wicf"],"links":[{"href":"https:\/\/icann.org\/wicf","type":"text\/html"}]}]}The first response from http://www.naughtytrigger.com, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with naughtytrigger.com. 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.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.