Skip to content

Hostname

logicallyfallacious.com

Last fetched

logicallyfallacious.com resolves to 34.237.161.9, announced in 34.224.0.0/12 by AMAZON-AES - Amazon.com, Inc. in US. logicallyfallacious.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 · logicallyfallacious.comRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/logicallyfallacious.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:440
Registrant organisation
igroops,
Contact emails
hostmaster@archieboy.com

Subdomains

Subdomain
beta.logicallyfallacious.com
mail.logicallyfallacious.com
mail2.logicallyfallacious.com
www.logicallyfallacious.com

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

  • ns35.domaincontrol.com
  • ns36.domaincontrol.com
  • ns55.domaincontrol.com
  • ns56.domaincontrol.com

MX records

  • mail.archieboy.com
  • mail.logicallyfallacious.com
  • mail2.logicallyfallacious.com

SPF policy

  • ip: 54.152.137.180/32
  • ip: 54.86.155.36/32
  • a: logicallyfallacious.com
  • mx: logicallyfallacious.com
  • a: scroops.com

Threat-feed evidence

History

Related pages

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