Hostname
lightning-bolt.com
Last fetched
lightning-bolt.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. lightning-bolt.com 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
No IPv4 resolution is recorded for lightning-bolt.com in WhisperGraph.
IPv6 resolution
No AAAA record for lightning-bolt.com is recorded in WhisperGraph.
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- 1964
- Contact emails
- suvas@lightning-bolt.com, 01258418-1e69-4c4b-8aee-d315b2170237@identity-protect.org, 5476a573-bba4-4b8d-ae2c-800fd27e1003@identity-protect.org, 5f5fcbc8-92c2-4377-82e2-c30fb4dd2305@identity-protect.org, 907ee452-fc00-4f1f-95f5-cbc52cf5506a@identity-protect.org, add078f2-3b8c-4123-85c0-8b4831135b4a@identity-protect.org, af7884e4-90cc-4d06-b098-7d3e4b1cf0d0@identity-protect.org, cb24b5d2-1bf2-4f91-b1cc-de2976ad156b@identity-protect.org, owner-11918557@lightning-bolt.com.whoisprivacyservice.org, owner-388245@lightning-bolt.com.whoisprivacyservice.org
Subdomains
Showing 12 of 122. View all subdomains →
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
Mail and authentication
Nameservers
- ns-370.awsdns-46.com
- ns-562.awsdns-06.net
- ns-1154.awsdns-16.org
- ns-2016.awsdns-60.co.uk
MX records
- lightningbolt-com02c.mail.protection.outlook.com
SPF policy
- include: amazonses.com
- include: aspmx.pardot.com
- include: mail.zendesk.com
Threat-feed evidence
History
Related pages
Pivot from lightning-bolt.com 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: "lightning-bolt.com"})-[: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.