Hostname

frantes.com

Last fetched Tue, 15 Sep 2026 14:54:05 GMT

frantes.com resolves to 104.26.2.165, announced in 104.26.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. frantes.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

Resolution chain

104.26.2.165
104.26.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
104.26.3.165
104.26.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
172.67.68.93
172.67.64.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
185.111.111.154
185.111.111.0/24 · CDNEXT - Datacamp Limited · Frankfurt am Main, DE
185.111.111.156
185.111.111.0/24 · CDNEXT - Datacamp Limited · Frankfurt am Main, DE
185.111.111.157
185.111.111.0/24 · CDNEXT - Datacamp Limited · Frankfurt am Main, DE
62.182.86.210
62.182.86.0/24 · YURTEH-AS - Virtual Systems LLC · Kyiv, UA

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar: iana:1479
Registrant organisation: danfra
Contact emails: 0fd0cf11ead34fd1accbfb2042adec48.protect@whoisguard.com, seremillonaria2015@hotmail.com, pw-a939285e62e12cd757404140997fcd7d@privacyguardian.org

Subdomains

Subdomain
mail.frantes.com
upload.frantes.com
webdisk.frantes.com
webmail.frantes.com
whm.frantes.com
www.frantes.com

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

lynn.ns.cloudflare.com
olga.ns.cloudflare.com
coco.bunny.net
kiki.bunny.net

MX records

mail.danfra.com

SPF policy

include: mail.danfra.com
include: spf.mailjet.com

Threat-feed evidence

History

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