Alternatives to jetbuzz.sbs
Matched automatically on description, category and technology. Only sites that pass our safety checks are shown. · Report a wrong match
jetbuzz.sbs was registered with Dynadot Inc on 22 Sept 2026. Its SSL certificate from Let's Encrypt is valid until 21 Dec 2026, and the site supports HTTP/3.
On-page basics for the homepage.
Networks cache previews — changes can take time to show.
What security vendors and the WOT community say about this domain.
0 of 5 protections set up
No SPF record: any server can send mail that claims to come from this domain.
—No key at the 12 common selectors we checked. A custom selector can’t be found from DNS alone.
—No DMARC policy: receivers aren’t told what to do with mail that fails SPF and DKIM.
—Forces encrypted delivery between mail servers.
—Shows the brand logo in supporting inboxes. Optional; needs DMARC enforcement.
—Read from the domain's public DNS records.
0 of 6 recommended headers
The page is served over plain HTTP, so HTTPS can’t be enforced.
Limits where scripts can load from — the main defence against XSS.
Stops the site being framed for clickjacking.
Prevents browsers guessing file types.
Which AI crawlers this site allows, and whether it publishes an llms.txt.
From robots.txt. “Partly blocked”: kept out of some pages, not the homepage. Not every crawler follows it. llms.txt is an optional guide some sites publish for AI assistants — it is not a ranking factor.
Pages and files that show who runs the site and how it handles data.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
Internet standards that make a site faster and safer.
The path from a typed address to the final page.
70 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| jetbuzz.lol | Other extension | 21 Sept 2026 | Active website | Report → |
| jetbuzz.homes | Other extension | 1 Sept 2026 | Active website | Report → |
| jetbuzz.link | Other extension | 1 Sept 2026 | Active website | Report → |
| jetbuzz.plus | Other extension | 1 Sept 2026 | Active website | Report → |
| jetbuzz.bar | Other extension | 27 Aug 2026 | Active website | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is jetbuzz.sbs’s name taken on other extensions?
Every IP address jetbuzz.sbs resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| jetbuzz.sbs | 104.21.45.20 | 300 |
| jetbuzz.sbs | 172.67.207.207 | 300 |
| Host | IPv6 address | TTL |
|---|---|---|
| jetbuzz.sbs | 2606:4700:3034::6815:2d14 | 300 |
| jetbuzz.sbs | 2606:4700:3034::ac43:cfcf | 300 |
| Host | Name server | TTL |
|---|---|---|
| jetbuzz.sbs | lynn.ns.cloudflare.com | 86400 |
| jetbuzz.sbs | robin.ns.cloudflare.com | 86400 |
| Host | Start of authority | TTL |
|---|---|---|
| jetbuzz.sbs | lynn.ns.cloudflare.com dns.cloudflare.com 2416389270 10000 2400 604800 1800 | 1800 |
No reviews yet. Used jetbuzz.sbs? 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.
jetbuzz.sbs has no community safety rating yet. Its SSL certificate is valid until 21 Dec 2026. See Security →
jetbuzz.sbs is registered through Dynadot Inc. See WHOIS →
The registration expires on 22 Sept 2027 — in 10 months. See Overview →
jetbuzz.sbs was registered on 22 Sept 2026, making it 1 month old. See Overview →
jetbuzz.sbs is served from 4 IP addresses, mainly on AS13335. See Hosting →
Raw registry data for jetbuzz.sbs. May be redacted by privacy services.
Domain Name: JETBUZZ.SBS Registry Domain ID: D646403532-CNIC Registrar WHOIS Server: whois.dynadot.com Registrar URL: http://www.dynadot.com Updated Date: 2026-09-29T06:33:00.0Z Creation Date: 2026-09-22T13:42:46.0Z Registry Expiry Date: 2027-09-22T23:59:59.0Z Registrar: Dynadot Inc Registrar IANA ID: 472 Domain Status: serverTransferProhibited https://icann.org/epp#serverTransferProhibited Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Name Server: LYNN.NS.CLOUDFLARE.COM Name Server: ROBIN.NS.CLOUDFLARE.COM DNSSEC: unsigned Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +1.6502620100 URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ >>> Last update of WHOIS database: 2026-11-01T10:02:00.0Z <<< For more information on Whois status codes, please visit https://icann.org/epp The registration data available in this service is limited. Additional data may be available at https://lookup.icann.org The Whois and RDAP services are provided by CentralNic, and contain information pertaining to Internet domain names registered by our our customers. By using this service you are agreeing (1) not to use any information presented here for any purpose other than determining ownership of domain names, (2) not to store or reproduce this data in any way, (3) not to use any high-volume, automated, electronic processes to obtain data from this service. Abuse of this service is monitored and actions in contravention of these terms will result in being permanently blacklisted. All data is (c) CentralNic Ltd (https://www.centralnicregistry.com) Access to the Whois and RDAP services is rate limited. For more information, visit https://centralnicregistry.com/policies/whois-guidance.
The first response from http://www.jetbuzz.sbs, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with jetbuzz.sbs. Data is collected independently from public sources and some figures are estimates, provided for information only.
Controls how much of the URL is shared with other sites.
Restricts camera, microphone and other browser features.
From the homepage's response, http://jetbuzz.sbs/
Spam and malware blocklists for the site's IP and mail servers.
When the site first appeared, and what has changed since.
No changes seen since we started recording on 1 Nov 2026.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.