Skip to content

Hostname

fring.io

Last fetched

fring.io resolves to 12 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in CZ. WHOIS lists iana:81 as the registrar.

Nutrition Label

WHISPER CANON · fring.ioRouting diversity3.0/10Peering density9.5/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/fring.io

Resolution chain

fring.io resolves to 12 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
13.227.192.5913.227.192.0/24AS16509AMAZON-02 - Amazon.com, Inc.CZ
13.227.192.7113.227.192.0/24AS16509AMAZON-02 - Amazon.com, Inc.CZ
13.227.192.8613.227.192.0/24AS16509AMAZON-02 - Amazon.com, Inc.CZ
13.227.192.9613.227.192.0/24AS16509AMAZON-02 - Amazon.com, Inc.CZ
13.249.98.11613.249.98.0/24AS16509AMAZON-02 - Amazon.com, Inc.US
13.249.98.12813.249.98.0/24AS16509AMAZON-02 - Amazon.com, Inc.US
13.249.98.2613.249.98.0/24AS16509AMAZON-02 - Amazon.com, Inc.US
13.249.98.9313.249.98.0/24AS16509AMAZON-02 - Amazon.com, Inc.US
3.171.139.1223.171.136.0/22AS16509AMAZON-02 - Amazon.com, Inc.US
3.171.139.283.171.136.0/22AS16509AMAZON-02 - Amazon.com, Inc.US
3.171.139.793.171.136.0/22AS16509AMAZON-02 - Amazon.com, Inc.US
3.171.139.83.171.136.0/22AS16509AMAZON-02 - Amazon.com, Inc.US

WHOIS identity

Registrar
iana:81
Organization
—
Contact emails
—

Subdomains

8 observed subdomains of fring.io.

Subdomain
briefing.fring.io
git.fring.io
home.fring.io
lidarr-spotify-sync.fring.io
music.fring.io
spotify-sync.fring.io
stream.fring.io
www.fring.io

Web-graph footprint

Distinct hostnames that link to or from fring.io in the public web crawl.

8 sites linked to from this hostname.

Sample inbound links

Sample outbound links

Threat posture

History

Mail and authentication

MX records

SPF policy

1 SPF mechanism authorising senders for fring.io.

MechanismTarget
SPF_INCLUDEspf.messagingengine.com

Related pages

Pivot deeper into the graph from fring.io.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

MATCH (h:HOSTNAME {name: "fring.io"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
      -[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.