Hostname
cigarettes.guru
Last fetched
cigarettes.guru resolves to 104.21.43.50, announced in 104.21.32.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. cigarettes.guru is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 104.21.43.50
104.21.32.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.220.12
172.67.208.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 68.66.216.9
68.66.216.0/21 · A2HOSTING - A2 Hosting, Inc. · Detroit, US
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1068
- Registrant organisation
- giannelis web services
- Contact emails
- c182fc1e6b6540db8a9815ad288a5aef.protect@withheldforprivacy.com, do-not-use@privacy-protected.email
Subdomains
| Subdomain |
|---|
| autodiscover.cigarettes.guru |
| cpanel.cigarettes.guru |
| cpcalendars.cigarettes.guru |
| cpcontacts.cigarettes.guru |
| mail.cigarettes.guru |
| webdisk.cigarettes.guru |
| webmail.cigarettes.guru |
| www.cigarettes.guru |
Showing 8 of 8 subdomains (8 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Sample outbound links
Mail and authentication
Nameservers
- ns1.a2hosting.com
- ns2.a2hosting.com
- ns3.a2hosting.com
- ns4.a2hosting.com
- damiete.ns.cloudflare.com
- meg.ns.cloudflare.com
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
MX records
- mail.cigarettes.guru
SPF policy
- include: spf.a2hosting.com
- a: cigarettes.guru
- mx: cigarettes.guru
- ip: 68.66.216.9
Threat-feed evidence
History
Related pages
Pivot from cigarettes.guru into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "cigarettes.guru"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.