good-pills.com, 718-487-9792, Scam

"good-pills.com" Registered by Paknic in Pakistan with no Registrant , Administrative or Technical Details what so ever. 718-487-9792 used in previous scams . Let me give you a bit more publicity .


+4420-3239-7092

+1-718-487-9792

http://good-pills.com/categories/Pain-Relief/all





"good-pills.com" AKA friendlypharmline.com, tadalaf20mg.com, genericcial.com, cialgeneri.com, sildenafdosage.com, mailordervia.com, cheapestcial.com, howtogetvia.com, Rxpillsbuyonline.com, FrambuesaRestaurante.com,
http://1-718-487-9792.com/ and many others



https://scamnumbers.info/forum/viewtopic.php?p=9199

http://phrmreviews.com/r/rxpillsbuyonli ... d-reviews/

http://phrmreviews.com/r/frambuesaresta ... us-origin/





https://whois.domaintools.com/good-pills.com



https://centralops.net/co/DomainDossier.aspx


Address lookup

canonical name good-pills.com.
aliases
addresses 109.236.81.34


Domain Whois record

Queried whois.internic.net with "dom good-pills.com"...
Domain Name: GOOD-PILLS.COM
Registry Domain ID: 2006319551_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.paknic.com
Registrar URL: http://www.paknic.com
Updated Date: 2016-08-17T06:54:26Z
Creation Date: 2016-02-25T13:35:07Z
Registry Expiry Date: 2018-02-25T13:35:07Z
Registrar: PakNIC (Private) Limited
Registrar IANA ID: 1367
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +1.7322978908
Domain Status: ok https://icann.org/epp#ok
Name Server: NS1.GOOD-PILLS.COM
Name Server: NS2.GOOD-PILLS.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2017-12-16T09:46:26Z <<<


Queried whois.paknic.com with "good-pills.com"...
Registry Domain ID: 2006319551_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.paknic.com
Registrar URL: http://www.paknic.com/
Updated Date: 2016-08-17T06:54:26Z
Creation Date: 2016-02-25T13:35:07Z
Registrar Registration Expiration Date: 2018-02-25T13:35:07Z
Registrar: Paknic Private Limited
Registrar IANA ID: 1367
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +92.4237421615
Reseller:
Registry Registrant ID:
Registrant Name:
Registrant Organization:
Registrant Street:
Registrant City:
Registrant State/Province:
Registrant Postal Code:
Registrant Country:
Registrant Phone:
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email:
Registry Admin ID:

https://www.icann.org/resources/pages/a ... s-accuracy

WHOIS ACCURACY PROGRAM SPECIFICATION

Registrar shall implement and comply with the requirements set forth in this Specification, as well as any commercially practical updates to this Specification that are developed by ICANN and the Registrar Stakeholder Group during the Term of the Registrar Accreditation Agreement.

1.Except as provided for in Section 3 below, within fifteen (15) days of (1) the registration of a Registered Name sponsored by Registrar, (2) the transfer of the sponsorship of a Registered Name to Registrar, or (3) any change in the Registered Name Holder with respect to any Registered Name sponsored by Registrar, Registrar will, with respect to both Whois information and the corresponding customer account holder contact information related to such Registered Name:

a.Validate the presence of data for all fields required under Subsection 3.3.1 of the Agreement in a proper format for the applicable country or territory.


b.Validate that all email addresses are in the proper format according to RFC 5322 (or its successors).


c.Validate that telephone numbers are in the proper format according to the ITU-T E.164 notation for international telephone numbers (or its equivalents or successors).


d.Validate that postal addresses are in a proper format for the applicable country or territory as defined in UPU Postal addressing format templates, the S42 address templates (as they may be updated) or other standard formats.


e.Validate that all postal address fields are consistent across fields (for example: street exists in city, city exists in state/province, city matches postal code) where such information is technically and commercially feasible for the applicable country or territory.


f.Verify:

i.the email address of the Registered Name Holder (and, if different, the Account Holder) by sending an email requiring an affirmative response through a tool-based authentication method such as providing a unique code that must be returned in a manner designated by the Registrar, or


ii.the telephone number of the Registered Name Holder (and, if different, the Account Holder) by either (A) calling or sending an SMS to the Registered Name Holder's telephone number providing a unique code that must be returned in a manner designated by the Registrar, or (B) calling the Registered Name Holder's telephone number and requiring the Registered Name Holder to provide a unique code that was sent to the Registered Name Holder via web, email or postal mail.




In either case, if Registrar does not receive an affirmative response from the Registered Name Holder, Registrar shall either verify the applicable contact information manually or suspend the registration, until such time as Registrar has verified the applicable contact information. If Registrar does not receive an affirmative response from the Account Holder, Registrar shall verify the applicable contact information manually, but is not required to suspend any registration.


2.Except as provided in Section 3 below, within fifteen (15) calendar days after receiving any changes to contact information in Whois or the corresponding customer account contact information related to any Registered Name sponsored by Registrar (whether or not Registrar was previously required to perform the validation and verification requirements set forth in this Specification in respect of such Registered Name), Registrar will validate and, to the extent required by Section 1, verify the changed fields in the manner specified in Section 1 above. If Registrar does not receive an affirmative response from the Registered Name Holder providing the required verification, Registrar shall either verify the applicable contact information manually or suspend the registration, until such time as Registrar has verified the applicable contact information. If Registrar does not receive an affirmative response from the Account Holder, Registrar shall verify the applicable contact information manually, but is not required to suspend any registration.


3.Except as set forth in paragraph 4 below, Registrar is not required to perform the above validation and verification procedures in Section 1(a) through 1(f) above, if Registrar has already successfully completed the validation and verification procedures on the identical contact information and is not in possession of facts or knowledge of circumstances that suggest that the information is no longer valid.


4.If Registrar has any information suggesting that the contact information specified in Section 1(a) through 1(f) above is incorrect (such as Registrar receiving a bounced email notification or non-delivery notification message in connection with compliance with ICANN's Whois Data Reminder Policy or otherwise) for any Registered Name sponsored by Registrar (whether or not Registrar was previously required to perform the validation and verification requirements set forth in this Specification in respect of such Registered Name), Registrar must verify or re-verify, as applicable, the email address(es) as described in Section 1.f (for example by requiring an affirmative response to a Whois Data Reminder Policy notice). If, within fifteen (15) calendar days after receiving any such information, Registrar does not receive an affirmative response from the Registered Name Holder providing the required verification, Registrar shall either verify the applicable contact information manually or suspend the registration, until such time as Registrar has verified the applicable contact information. If, within fifteen (15) calendar days after receiving any such information, Registrar does not receive an affirmative response from the customer paying for the Registered Name, if applicable, providing the required verification, Registrar shall verify the applicable contact information manually, but is not required to suspend any registration.


5.Upon the occurrence of a Registered Name Holder's willful provision of inaccurate or unreliable WHOIS information, its willful failure promptly to update information provided to Registrar, or its failure to respond for over fifteen (15) calendar days to inquiries by Registrar concerning the accuracy of contact details associated with the Registered Name Holder's registration, Registrar shall either terminate or suspend the Registered Name Holder's Registered Name or place such registration on clientHold and clientTransferProhibited, until such time as Registrar has validated the information provided by the Registered Name Holder.


6.The terms and conditions of this Specification shall be reviewed by ICANN in consultation with the Registrar Stakeholder Group on or about the first anniversary of the date that the form of this Agreement is first executed by a registrar.


7.Nothing within this Specification shall be deemed to require Registrar to perform verification or validation of any customer account holder information where the customer account holder does not have any Registered Names under sponsorship of Registrar.