Hostname
dev.lossdog.com
Last fetched
dev.lossdog.com resolves to 3.160.188.100, announced in 3.160.188.0/23 by AMAZON-02 - Amazon.com, Inc. in FR. dev.lossdog.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
- 3.160.188.100
3.160.188.0/23 · AMAZON-02 - Amazon.com, Inc. · Marseille, FR
- 3.160.188.113
3.160.188.0/23 · AMAZON-02 - Amazon.com, Inc. · Marseille, FR
- 3.160.188.13
3.160.188.0/23 · AMAZON-02 - Amazon.com, Inc. · Marseille, FR
- 3.160.188.25
3.160.188.0/23 · AMAZON-02 - Amazon.com, Inc. · Marseille, FR
- 3.168.147.117
3.168.144.0/21 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 3.168.147.25
3.168.144.0/21 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 3.168.147.65
3.168.144.0/21 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 3.168.147.77
3.168.144.0/21 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
IPv6 resolution
No AAAA record for dev.lossdog.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for dev.lossdog.com. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Subdomains
| Subdomain |
|---|
| alb.dev.lossdog.com |
| api-eks.dev.lossdog.com |
| api.dev.lossdog.com |
| biz.dev.lossdog.com |
| live-shows.dev.lossdog.com |
| pe.dev.lossdog.com |
| streamer.dev.lossdog.com |
Showing 7 of 7 subdomains (7 per page).
Mail and authentication
Nameservers
- ns-467.awsdns-58.com
- ns-776.awsdns-33.net
- ns-1483.awsdns-57.org
- ns-1663.awsdns-15.co.uk
Threat-feed evidence
History
Related pages
Pivot from dev.lossdog.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: "dev.lossdog.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.