Hostname
reisys.com
Last fetched
reisys.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. reisys.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 reisys.com in WhisperGraph.
IPv6 resolution
No AAAA record for reisys.com is recorded in WhisperGraph.
WHOIS identity
- Registrar
- iana:2
- Registrant organisation
- perfect privacy,
- Contact emails
- dr6934y64z8@networksolutionsprivateregistration.com, jp7z65f26fb@networksolutionsprivateregistration.com, kpsingh@reisys.com, m25xs8499b4@networksolutionsprivateregistration.com, ms6gw8ac3wm@networksolutionsprivateregistration.com, my4cx38t2tw@networksolutionsprivateregistration.com, q92hn93b5nf@networksolutionsprivateregistration.com, qa7ag9gk4ve@networksolutionsprivateregistration.com, rh3ec6sa7j8@networksolutionsprivateregistration.com, tq8cd4kv8fz@networksolutionsprivateregistration.com, ue7dp3xk5g6@networksolutionsprivateregistration.com, vt8wu4yp4ar@networksolutionsprivateregistration.com, wt9bb47w4j7@networksolutionsprivateregistration.com, ym7ag8mq93e@networksolutionsprivateregistration.com
Subdomains
Mail and authentication
Nameservers
- dns01.reisys.com
- dns03.reisys.com
- dns05.reisys.com
- dns07.reisys.com
- dnsmaster.reisys.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
- reisys-com.mail.protection.outlook.com
SPF policy
- include: spf.protection.outlook.com
- mx: reisys.com
- ip: 65.242.96.72
- ip: 65.242.97.32
- ip: 65.242.97.90
- ip: 65.242.97.91
Threat-feed evidence
History
Related pages
Pivot from reisys.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: "reisys.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.