Skip to content

Hostname

ulandka.com

Last fetched

ulandka.com resolves to 104.26.10.191, announced in 104.26.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. ulandka.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 · ulandka.comRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/ulandka.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · MAIL_RECEIVER, ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1456
Registrant organisation
whois data protection sp. z o.o.
Contact emails
ddbrcmxlunyg-r@mail.netart-registrar.com, hfyusykhefkc-r@mail.netart-registrar.com, iywyskgsvldo-r@mail.netart-registrar.com, qabipihovqyd-r@mail.netart-registrar.com, ygbyefasutij-r@mail.netart-registrar.com, drfdkennrjnh-r@mail.whoisdataprotection.com, giesrbfoqpbi-r@mail.whoisdataprotection.com, yiusuwcdhpqt-r@mail.whoisdataprotection.com

Subdomains

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

  • celeste.ns.cloudflare.com
  • derek.ns.cloudflare.com
  • 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

MX records

  • smtp.google.com
  • ulandka.com
  • _dc-mx.0bc9f07d1fc3.ulandka.com

SPF policy

  • include: _spf.getresponse.com
  • include: _spf.google.com
  • a: ulandka.com
  • mx: ulandka.com
  • include: _spf.cyberfolks.pl
  • ip: 195.2.222.89

Threat-feed evidence

History

Related pages

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