Hostname
relaysteering.com
Last fetched
relaysteering.com resolves to 135.148.136.13, announced in 135.148.128.0/17 by OVH - OVH SAS in US. relaysteering.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
- 135.148.136.13
135.148.128.0/17 · OVH - OVH SAS · Reston, US
- 135.148.150.106
135.148.128.0/17 · OVH - OVH SAS · Reston, US
- 135.148.151.114
135.148.128.0/17 · OVH - OVH SAS · Reston, US
- 135.148.151.115
135.148.128.0/17 · OVH - OVH SAS · Reston, US
- 135.148.151.118
135.148.128.0/17 · OVH - OVH SAS · Reston, US
- 135.148.151.34
135.148.128.0/17 · OVH - OVH SAS · Reston, US
- 135.148.151.99
135.148.128.0/17 · OVH - OVH SAS · Reston, US
- 141.94.94.48
141.94.0.0/16 · OVH - OVH SAS · Roubaix, FR
- 141.94.96.67
141.94.0.0/16 · OVH - OVH SAS · Strasbourg, FR
- 141.95.146.59
141.95.128.0/17 · OVH - OVH SAS · Strasbourg, FR
- 148.113.153.123
- 148.113.153.125
- 148.113.153.126
- 148.113.206.32
- 148.113.206.33
- 15.235.212.156
- 15.235.212.17
- 15.235.212.94
- 15.235.215.25
- 15.235.216.148
IPv6 resolution
No AAAA record for relaysteering.com is recorded in WhisperGraph.
Attribution
ovh
ORIGIN_AS
WHOIS identity
- Registrar
- iana:168
- Registrant organisation
- bad kitty's dad, lda
Subdomains
Showing 2 of 4. View all subdomains →
Mail and authentication
Nameservers
- micah.ns.cloudflare.com
- tegan.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
Threat-feed evidence
History
Related pages
Pivot from relaysteering.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: "relaysteering.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.