Skip to content

Hostname

aandrc.com

Last fetched

aandrc.com resolves to 216.92.27.117, announced in 216.92.0.0/16 by PAIR-NETWORKS - pair Networks in US. aandrc.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 · aandrc.comRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.0/10canon.whisper.security/host/aandrc.com

Resolution chain

IPv6 resolution

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

Attribution

pair

ORIGIN_AS

WHOIS identity

Registrar
iana:99
Registrant organisation
james a. lawler
Contact emails
013q3j8s6705@filteredemailaddress.com, 02126p7x9590@nojunkemailaddress.com, 11031h9e3757@junkemailprevention.com, 117p3c4y8863@eliminatejunkemail.com, 1x8u9d8910@junkemailprevention.com, 3o1r484555@junkemailprevention.com, 3y1l3d7549@junkemailprevention.com, 4q1z2h8322@junkemailprevention.com, 4u5o008349@junkemailprevention.com, 514v778t4259@filteredemailaddress.com, 518r2y3p9532@junkemailprevention.com, 51945g1x1331@nojunkemailaddress.com, 612p1i2o9007@filteredemailaddress.com, 6r264f2101@junkemailprevention.com, 7441898908@nojunkemailaddress.com, 81226n744789@junkemailprevention.com

Subdomains

Showing 2 of 2 subdomains (2 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.

Mail and authentication

Nameservers

  • ns00.ns0.com
  • ns100.pair.com
  • ns542.pair.com

MX records

  • mailwash57.pair.com

SPF policy

  • mx: aandrc.com
  • a: digitalriver.com
  • a: kaskal.pair.com
  • a: mailwash57.pair.com
  • include: relay.pair.com
  • include: webmail.pair.com
  • include: pairlist.com
  • a: plimus.com
  • include: comcast.net

Threat-feed evidence

History

Related pages

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