Skip to content

Hostname

wtvq.com

Last fetched

wtvq.com resolves to 192.104.183.130, announced in 192.104.183.0/24 by LEE-ASN - Lee Enterprises, Incorporated in US. wtvq.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 · wtvq.comRouting diversity1.5/10Peering density2.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint9.0/10canon.whisper.security/host/wtvq.com

Resolution chain

IPv6 resolution

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

Attribution

lee enterprises incorporated

ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
alexandria graham
Contact emails
agraham@wtvq.com, rwallace@wtvq.com

Subdomains

Subdomain
circulars.wtvq.com
demo.wtvq.com
enps.wtvq.com
ex1.wtvq.com
ftp.wtvq.com
hub.wtvq.com
rcms.wtvq.com
www.wtvq.com

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

Mail and authentication

Nameservers

  • ns-493.awsdns-61.com
  • ns1.linode.com
  • ns2.linode.com
  • ns3.linode.com
  • ns4.linode.com
  • ns5.linode.com
  • ns-906.awsdns-49.net
  • 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
  • ns-1269.awsdns-30.org
  • ns-1605.awsdns-08.co.uk

MX records

  • wtvq-com.mail.protection.outlook.com
  • mxa-0028be01.gslb.pphosted.com
  • mxb-0028be01.gslb.pphosted.com

SPF policy

  • include: spf.protection.outlook.com
  • include: woexchange.com

Threat-feed evidence

History

Related pages

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