fc2.us - DNS, WHOIS, DMARC and SPF of the domain name

Summary

Registrar: eNom, LLC
Status: clientTransferProhibited
Created on: May 9, 2002
Expires on: May 9, 2027
Name servers: dns4.name-services.com, dns1.name-services.com, dns2.name-services.com, dns3.name-services.com
Mail servers: ASPMX.L.GOOGLE.COM, ALT1.ASPMX.L.GOOGLE.COM, ALT2.ASPMX.L.GOOGLE.COM, ASPMX2.GOOGLEMAIL.COM, ASPMX3.GOOGLEMAIL.COM
DMARC: Monitoring
SPF: Soft
DKIM: 2 keys found
Website: See the website

Spoofing protection (DMARC)

Monitoring

E-mails spoofing this domain are only reported, not blocked.

DMARC tells mail servers what to do with an e-mail that claims to come from fc2.us but fails SPF and DKIM checks.

Policy: Monitoring
Subdomain policy: Monitoring
Messages covered: 100%
DKIM alignment: Relaxed
SPF alignment: Relaxed
Aggregate reports: [email protected]
Failure reports: —

Record

v=DMARC1; p=none; rua=mailto:[email protected]

Authorized senders (SPF)

Soft

E-mails sent by any other server are accepted but flagged as suspicious.

SPF lists the servers allowed to send e-mails for fc2.us.

Rule	Value	Result
include	spf-old-mail1.fc2.com	Allowed
ip4	54.244.35.137	Allowed
include	spf-mail-mobile.fc2.com	Allowed
ip4	208.71.104.0/24	Allowed
include	_spf.google.com	Allowed
all	—	Suspicious

Top-level DNS lookups: 3 of 10 allowed

Record

v=spf1 include:spf-old-mail1.fc2.com ip4:54.244.35.137 include:spf-mail-mobile.fc2.com ip4:208.71.104.0/24 include:_spf.google.com ~all

E-mail signing (DKIM)

DKIM keys published by fc2.us under the most common selectors. Other keys may exist under selectors specific to each sending service.

Selector	Likely service	Key	Status
google	Google Workspace	RSA 1024 bits · short	Active
s1	SendGrid	RSA 2048 bits	Active

RSA keys shorter than 2048 bits, called short keys, are discouraged: they are easier to break.

MX, SPF, DKIM and DMARC: the e-mail records

Four DNS records make a domain's e-mail work. MX says where e-mails sent to fc2.us arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from fc2.us was really sent by this domain, which protects it against spoofing.

MX

An MX (Mail Exchanger) record designates a server that receives e-mails sent to the domain. When someone writes to an @fc2.us address, their mail server queries the DNS for the domain's MX records, then delivers the message to the server they point to.

Example record

fc2.us  MX  10 mx1.fc2.us.
fc2.us  MX  20 mx2.fc2.us.

What the record contains

10, 20: Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
mx1.fc2.us.: Host name of the mail server. It must point to an A or AAAA record: an IP address or an alias (CNAME) is not allowed here.
0 .: An MX "0 .", called a null MX, declares that the domain accepts no e-mail: sending servers give up at once instead of retrying.

Declaring at least two servers with different priorities avoids losing e-mails during an outage: sending servers retry for several days and fall back on the backup server. Without any MX, they try to deliver directly to the IP address of the domain.

SPF

SPF (Sender Policy Framework) is a TXT record listing the servers allowed to send e-mails on behalf of the domain. The receiving server checks that the sender is on this list. The final "all" rule says what to do with other servers: reject them (-all), flag their e-mails as suspicious (~all) or make no decision (?all).

Example record

fc2.us  TXT  "v=spf1 mx include:_spf.google.com ip4:192.0.2.10 -all"

What the record contains

v=spf1: Identifies the record as an SPF policy. It must come first.
ip4, ip6: Allows a specific IP address or an address range, for example ip4:192.0.2.0/24.
a, mx: Allows the addresses of the domain itself (A record) or those of its mail servers (MX).
include: Allows the servers of another domain, usually a sending service: include:_spf.google.com for Google Workspace.
-all, ~all: Final rule, applied to every other server. Its qualifier decides what happens to them: - rejects them, ~ flags their e-mails as suspicious, ? makes no decision, + accepts them (avoid it).

A domain must publish only one SPF record, and its evaluation cannot exceed 10 DNS lookups (include, a, mx, exists, redirect). Beyond that, mail servers treat it as invalid.

DKIM

DKIM (DomainKeys Identified Mail) signs every outgoing e-mail with a private key. The matching public key is published in a TXT record at selector._domainkey.fc2.us, so the recipient can check that the message really comes from the domain and was not altered on the way. The selector is chosen by each sending service and cannot be guessed: Dataweaz checks the most common ones (Google Workspace, Microsoft 365, Mailchimp, SendGrid…), so a key published under another selector may exist without appearing here.

Example record

google._domainkey.fc2.us  TXT  "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA…"

What the record contains

v=DKIM1: Protocol version. Optional but recommended, in which case it must come first.
k: Key algorithm: rsa, the most common, or ed25519.
p: Public key, base64-encoded. An empty value means the key has been revoked.
t: Flags: y marks a key in testing, whose failures must not be penalized; s forbids its use for subdomains.

Each sending service publishes its key under its own selector (google, selector1, k1…), which allows several keys and seamless rotation. A 2048-bit RSA key is recommended today.

DMARC

DMARC (Domain-based Message Authentication, Reporting and Conformance) builds on SPF and DKIM. Published on _dmarc.fc2.us, it tells mail servers what to do with an e-mail that fails these checks (let it through, send it to spam or reject it) and where to send reports.

Example record

_dmarc.fc2.us  TXT  "v=DMARC1; p=quarantine; rua=mailto:[email protected]; adkim=r; aspf=r"

What the record contains

v=DMARC1: Identifies the record as a DMARC policy. It must come first.
p: Policy applied to e-mails that fail the checks: none (monitoring only), quarantine (spam folder) or reject.
sp: Subdomain policy. Without it, subdomains follow the domain's policy.
rua: Address that receives daily aggregate reports about e-mails sent on behalf of the domain, whether they pass the checks or not.
ruf: Address that receives detailed failure reports, message by message. Few providers still send them.
pct: Percentage of e-mails subject to the policy, for a gradual rollout. 100 by default.
adkim, aspf: DKIM and SPF alignment: r (relaxed, a subdomain of the same domain is enough) or s (strict, the domain must be identical).

To roll out DMARC without blocking legitimate e-mails, start with p=none and an rua address, analyze the reports to find every service sending on behalf of the domain, then move to quarantine and finally to reject.

DNS records of fc2.us

IP addresses (A and AAAA)

An A record maps the domain name to an IPv4 address: the address of the server that browsers contact to display the website. The AAAA record does the same for an IPv6 address. A domain can have several of them to spread visits across several servers.

No IP address: the domain does not point to any web server.

Name servers (NS)

NS records designate the authoritative DNS servers of the domain: they answer every question about its other records (A, MX, TXT…). They are provided by the registrar, the hosting provider or a dedicated DNS service, and several servers are declared so that the domain keeps working if one of them fails.

Server	IP address
dns4.name-services.com	216.40.47.202
dns1.name-services.com	64.98.148.137
dns2.name-services.com	216.40.47.201
dns3.name-services.com	64.98.148.138

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @fc2.us addresses. Each server has a priority: the one with the lowest number is tried first, the others take over if it fails. Without an MX record, the domain cannot receive e-mails.

Priority	Server	IP address
10	ASPMX.L.GOOGLE.COM	74.125.71.26
20	ALT1.ASPMX.L.GOOGLE.COM	192.178.213.27
30	ALT2.ASPMX.L.GOOGLE.COM	142.251.127.26
40	ASPMX2.GOOGLEMAIL.COM	192.178.213.27
50	ASPMX3.GOOGLEMAIL.COM	142.251.127.26

TXT records

TXT records hold free text. They are used to prove ownership of the domain to online services (Google, Microsoft, Facebook…) and to publish e-mail security rules: SPF on the domain itself, DMARC on _dmarc.fc2.us.

Name	Content
fc2.us	v=spf1 include:spf-old-mail1.fc2.com ip4:54.244.35.137 include:spf-mail-mobile.fc2.com ip4:208.71.104.0/24 include:_spf.google.com ~all
fc2.us	apple-domain-verification=kjVRQphcsWskvaFG
_dmarc.fc2.us	v=DMARC1; p=none; rua=mailto:[email protected]
google._domainkey.fc2.us	v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCn5TcEkNah/g0RXbIkOtNgS4pbrrvTLoYghoYH3HFTdZk7Q4ad77HvOh6O39r8l6IS6elPjF3QJfPO4CMlRw6WlnWib6ooovkNCMckU5LBZzoonVp8h0Swfo4QQ1NKixLp5yiPsbRJsgsjwe3+++zBdxGChxklu3csSmge3wWJKwIDAQAB
s1._domainkey.fc2.us	v=DKIM1; h=sha256; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsjjwRX9BeixAGTk+bVAb6NmZ+s7bcRyU3J/SWZJFtAU2HxI3cHMvZyCbJFRrFkbIMu3BAoRTDmppbbMp9fMMu60UIkFu93u6vQgHa0hkZEc5fqiETcNFFYeGUttyVu2m6y0WbSCNhtbiYtuZQmzc3waV3IQQJn4iVGtenQLrloqrnuVm2jRFDCtd8Zqpl5PbC2oSjGUi1mdmOdojHMWlRnHYjvEBtQlgyn3t348hSfxRnLPZjUMIxaV3aj7kR6Zz84KikYQ9iEBL/d+26ysuJYy9nOXRpxGvJaX4KIdA1xoh/KRixbO4QRLlLfwv/gDIikSJzP6xOkYoj/Yu2Ff02QIDAQAB

Related IP addresses

IPv4 addresses used by fc2.us: website, name servers, mail servers and senders authorized by SPF.

IP address	Used for	/24 block
216.40.47.202	Name server dns4.name-services.com	216.40.47.0/24
64.98.148.137	Name server dns1.name-services.com	64.98.148.0/24
216.40.47.201	Name server dns2.name-services.com	216.40.47.0/24
64.98.148.138	Name server dns3.name-services.com	64.98.148.0/24
74.125.71.26	Mail server ASPMX.L.GOOGLE.COM	74.125.71.0/24
192.178.213.27	Mail server ALT1.ASPMX.L.GOOGLE.COM, Mail server ASPMX2.GOOGLEMAIL.COM	192.178.213.0/24
142.251.127.26	Mail server ALT2.ASPMX.L.GOOGLE.COM, Mail server ASPMX3.GOOGLEMAIL.COM	142.251.127.0/24
54.244.35.137	Authorized by SPF	54.244.35.0/24

WHOIS of the domain fc2.us

Domain Name: fc2.us
Registry Domain ID: D2330516-US
Registrar WHOIS Server: whois.enom.com
Registrar URL: whois.enom.com
Updated Date: 2026-04-14T06:40:29Z
Creation Date: 2002-05-09T10:21:44Z
Registry Expiry Date: 2027-05-08T23:59:59Z
Registrar: eNom, LLC
Registrar IANA ID: 48
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +1.4165350123
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: C96BD7D27AA5C4D9BAFF6129BE151E1B8-GDREG
Registrant Name: DNS ADMIN
Registrant Organization: FC2,inc.
Registrant Street: 4730 South Fort Apache Road
Registrant Street: Suite 300
Registrant Street:
Registrant City: Las Vegas
Registrant State/Province: NV
Registrant Postal Code: 89147
Registrant Country: US
Registrant Phone: +1.7026169916
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: [email protected]
Registrant Application Purpose: P3
Registrant Nexus Category: C11
Registry Admin ID: C6354E746D8EF4E4EB1C8196EB38755E4-GDREG
Admin Name: DNS ADMIN
Admin Organization: FC2,inc.
Admin Street: 4730 South Fort Apache Road
Admin Street: Suite 300
Admin Street:
Admin City: Las Vegas
Admin State/Province: NV
Admin Postal Code: 89147
Admin Country: US
Admin Phone: +1.7026169916
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: [email protected]
Registry Tech ID: C07B52AEE526B46099F6286CB8210ED01-GDREG
Tech Name: DNS ADMIN
Tech Organization: FC2,inc.
Tech Street: 4730 South Fort Apache Road
Tech Street: Suite 300
Tech Street:
Tech City: Las Vegas
Tech State/Province: NV
Tech Postal Code: 89147
Tech Country: US
Tech Phone: +1.7026169916
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: [email protected]
Name Server: dns4.name-services.com
Name Server: dns3.name-services.com
Name Server: dns2.name-services.com
Name Server: dns1.name-services.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2026-10-02T03:51:49Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

.US WHOIS Complaint Tool - http://www.whoiscomplaints.us
Advanced WHOIS Instructions - http://whois.us/help.html

Registry Services, LLC, the Registry Administrator for .US, has collected this information for the WHOIS database through a .US-Accredited Registrar. This information is provided to you for informational purposes only and is designed to assist persons in determining contents of a domain name registration record in the registry database. 

Registry Services, LLC makes this information available to you "as is" and does not guarantee its accuracy. By submitting a WHOIS query, you agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data: 

(1) to allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via direct mail, electronic mail, or by telephone; 
(2) in contravention of any applicable data and privacy protection laws; or 
(3) to enable high volume, automated, electronic processes that apply to the registry (or its systems). 

Compilation, repackaging, dissemination, or other use of the WHOIS database in its entirety, or of a substantial portion thereof, is not allowed without our prior written permission. 

We reserve the right to modify or change these conditions at any time without prior or subsequent notification of any kind. By executing this query, in any manner whatsoever, you agree to abide by these terms. NOTE: FAILURE TO LOCATE A RECORD IN THE WHOIS DATABASE IS NOT INDICATIVE OF THE AVAILABILITY OF A DOMAIN NAME. All domain names are subject to certain additional domain name registration rules. For details, please visit our site at www.whois.us.


Domain Name: fc2.us
Registry Domain ID: D2330516-US
Registrar WHOIS Server: WHOIS.ENOM.COM
Registrar URL: WWW.ENOMDOMAINS.COM
Updated Date: 2026-04-14T06:40:29.04Z
Creation Date: 2002-05-09T10:21:44.00Z
Registrar Registration Expiration Date: 2027-05-08T23:59:00.00Z
Registrar: ENOM, INC.
Registrar IANA ID: 48
Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant Street: 
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: NV
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: US
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: 
Registrant Fax: REDACTED FOR PRIVACY
Registrant Email: https://tieredaccess.com/contact/6e2598c0-06bd-4d16-94c6-f96e09b87490
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Street: 
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: 
Admin Fax: REDACTED FOR PRIVACY
Admin Email: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Street: 
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: 
Tech Fax: REDACTED FOR PRIVACY
Tech Email: REDACTED FOR PRIVACY
Name Server: DNS1.NAME-SERVICES.COM
Name Server: DNS2.NAME-SERVICES.COM
Name Server: DNS3.NAME-SERVICES.COM
Name Server: DNS4.NAME-SERVICES.COM
DNSSEC: unsigned
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +1.4259744689
URL of the ICANN WHOIS Data Problem Reporting System: HTTP://WDPRS.INTERNIC.NET/
>>> Last update of WHOIS database: 2026-10-02T03:51:50.00Z <<<

For more information on Whois status codes, please visit https://icann.org/epp


The data in this whois database is provided to you for information
purposes only, that is, to assist you in obtaining information about or
related to a domain name registration record. We make this information
available "as is," and do not guarantee its accuracy. By submitting a
whois query, you agree that you will use this data only for lawful
purposes and that, under no circumstances will you use this data to: (1)
enable high volume, automated, electronic processes that stress or load
this whois database system providing you this information; or (2) allow,
enable, or otherwise support the transmission of mass unsolicited,
commercial advertising or solicitations via direct mail, electronic
mail, or by telephone. The compilation, repackaging, dissemination or
other use of this data is expressly prohibited without prior written
consent from us.  

We reserve the right to modify these terms at any time. By submitting 
this query, you agree to abide by these terms.
Version 6.3 4/3/2002

% Query time: 1703 msec
% WHEN: Fri Oct 02 03:51:48 UTC 2026