Skip to content

Hostname

wdtimes.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

lee enterprises incorporated

ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
apg media of wisconsin
Contact emails
domains@adamspg.com, hostmaster@kdimail.com, noreply@data-protected.net

Subdomains

Subdomain
m.wdtimes.com
tollbit.wdtimes.com
wd-www2.wdtimes.com
www.wdtimes.com
www2.wdtimes.com

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

  • ns0.dnsmadeeasy.com
  • ns1.dnsmadeeasy.com
  • ns2.dnsmadeeasy.com
  • ns3.dnsmadeeasy.com
  • ns4.dnsmadeeasy.com

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: bluehost.com
  • include: spf.brevo.com
  • include: ccsend.com
  • include: confirmedcc.com
  • include: spf.constantcontact.com
  • include: emailsrvr.com
  • include: _spf.google.com
  • include: secondstreetmail.com
  • include: spf.sendinblue.com
  • mx: wdtimes.com
  • include: prodcc.net

Threat-feed evidence

History

Related pages

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