Skip to content

Hostname

rdysl.com

Last fetched

rdysl.com resolves to 66.39.130.30, announced in 66.39.128.0/19 by PAIR-NETWORKS - pair Networks in US. rdysl.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · rdysl.comRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/rdysl.com

Resolution chain

IPv6 resolution

No AAAA record for rdysl.com is recorded in WhisperGraph.

Attribution

pair

ORIGIN_AS

WHOIS identity

Registrar
iana:30
Registrant organisation
mark vandellon
Contact emails
b324y52w6uy@namesecureprivatename.com, bd3uw8hy3nz@myprivatename.com, gw5nd7gz5qy@nameprivacy.com, h73n92k76av@nameprivacy.com, md3xp79a48t@nameprivacy.com, qq6y59qe6he@namesecureprivatename.com, mvandel1@rochester.rr.com

Subdomains

Subdomain
www.rdysl.com

Showing 1 of 1 subdomain (1 per page).

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

Sample outbound links

Mail and authentication

Nameservers

  • ns0000.ns0.com
  • ns529.pair.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

  • vqs3931.pair.com

SPF policy

  • include: relay.pair.com
  • a: vqs3931.pair.com
  • include: webmail.pair.com
  • include: pairlist.com

Threat-feed evidence

History

Related pages

Pivot from rdysl.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: "rdysl.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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.