Hostname
thelightsource.com
Last fetched
thelightsource.com resolves to 8 IPv4 addresses operated by AMAZON-AES - Amazon.com, Inc. in US. WHOIS lists iana:1068 as the registrar.
Nutrition Label
Resolution chain
thelightsource.com resolves to 8 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 16.15.178.159 | 16.15.176.0/21 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 16.15.180.142 | 16.15.176.0/21 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 16.182.105.133 | 16.182.96.0/20 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.5.14.167 | 3.5.14.0/23 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.5.30.208 | 3.5.30.0/23 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.217.126.173 | 52.217.112.0/20 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.217.95.141 | 52.217.95.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 54.231.161.149 | 54.231.160.0/19 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
WHOIS identity
- Registrar
- iana:1068
- Organization
- daniel von fange
- Contact emails
Subdomains
3 observed subdomains of thelightsource.com.
Web-graph footprint
Distinct hostnames that link to or from thelightsource.com in the public web crawl.
Sample inbound links
Threat posture
History
Mail and authentication
SPF policy
4 SPF mechanisms authorising senders for thelightsource.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | servers.mcsv.net |
| SPF_INCLUDE | spf.ess.barracudanetworks.com |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_IP | 12.19.59.242 |
Related pages
Pivot deeper into the graph from thelightsource.com.
- IP · 16.15.178.159
- ASN · AS14618AMAZON-AES - Amazon.com, Inc.
- Registrar · iana:1068
- Country · US
- Email · daniel@leancoder.com
- TLD · .com
- Browse hostnames · th…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "thelightsource.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.