Skip to content

Hostname

lacek.net

Last fetched

lacek.net resolves to 209.98.208.7, announced in 209.98.128.0/17 by US-SIGNAL-MN01 - US Signal Company, L.L.C. in US. lacek.net 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 · lacek.netRouting diversity1.5/10Peering density3.6/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/lacek.net

Resolution chain

IPv6 resolution

No AAAA record for lacek.net is recorded in WhisperGraph.

Attribution

us signal

ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
domains by proxy,
Contact emails
dnsadmin@lacek.com

Subdomains

Mail and authentication

Nameservers

  • ns37.domaincontrol.com
  • ns38.domaincontrol.com

MX records

  • mail.lg4.net

SPF policy

  • ip: 148.105.0.0/16
  • ip: 198.2.128.0/18
  • ip: 205.201.128.0/20
  • ip: 173.203.179.0/24
  • ip: 209.98.208.0/24
  • ip: 207.97.220.0/24
  • ip: 209.98.46.1/32
  • ip: 199.229.91.1/32
  • ip: 35.162.185.109/32
  • ip: 34.218.14.129/32
  • ip: 52.89.12.139/32
  • ip: 52.26.166.151/32
  • ip: 34.215.209.152/32
  • ip: 54.186.77.157/32
  • ip: 52.32.252.160/32
  • ip: 52.43.57.175/32
  • ip: 52.37.7.197/32
  • ip: 54.187.251.2/32
  • ip: 52.40.63.2/32
  • ip: 52.40.63.21/32
  • ip: 35.163.242.214/32
  • ip: 34.212.62.239/32
  • ip: 52.88.240.248/32
  • ip: 208.42.28.25/32
  • ip: 52.37.10.250/32
  • ip: 38.142.93.250/32
  • ip: 52.40.63.34/32
  • ip: 52.40.63.35/32
  • ip: 209.98.208.5/32
  • ip: 52.39.128.55/32
  • ip: 52.40.63.61/32
  • ip: 34.217.183.70/32
  • ip: 52.89.47.9/32
  • ip: 52.37.178.91/32
  • ip: 52.43.116.95/32
  • include: servers.mcsv.net

Threat-feed evidence

History

Related pages

Pivot from lacek.net 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: "lacek.net"})-[: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.